Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve error handling when a device is not present in BlueZ #1511

Merged
merged 2 commits into from
Feb 20, 2024

Conversation

Siecje
Copy link
Contributor

@Siecje Siecje commented Feb 14, 2024

Fixes #1507

@Siecje Siecje force-pushed the bluez_not_found branch 2 times, most recently from b949f2d to c9bc45a Compare February 14, 2024 13:57
bleak/backends/bluezdbus/manager.py Outdated Show resolved Hide resolved
bleak/backends/bluezdbus/manager.py Outdated Show resolved Hide resolved
@dlech
Copy link
Collaborator

dlech commented Feb 14, 2024

This isn't a trivial change, so I would like to add a commit message explaining the reason why these changes are needed and also add a changelog entry for the fix. Thanks!

@dlech dlech merged commit ae22bdb into hbldh:develop Feb 20, 2024
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

KeyError: 'org.bluez.Device1'
2 participants